Get Connected!
Come and join our community. Expand your network and get to know new people!
Not sure it is directly related, but each time I connect my Atik camera, I get these errors:
2024-05-09T17:56:19: Driver indi_atik_ccd: No IText 'FITS_OBJECT' in Atik 460ex.FITS_HEADER
2024-05-09T17:56:19: Driver indi_atik_ccd: indi_atik_ccd dispatch error: Property TELESCOPE_TYPE is not defined in Atik 460ex.The camera seems to work correctly, so these errors might be just warnings. In that case, why are they displayed ?
Using the 2.0.7 Indi version. And I got the same behaviour with the previous flavour.
Read More...
INDI 1.9.7 is old. Try update to latest one. If you have latest KStars with old INDI there can be additional bugs as they are quite tightly coupled.
Read More...
- Yes, you can connect to local and remote INDI servers at the same time.
- Yes, the client (Ekos) constructs the GUI from the drivers declared properties.
Read More...
This question may be a little to involved to get a complete answer .. I'd just like some opinions on whether I'm on the right track. Thanks in advance.
I'm building a Skyshed roll-off roof observatory. I have a small form factor PC running my main Indi server (mount, imagers, focuser etc.). In addition I wan another smaller (old raspberry pi or Arduino) that is always powered up and has a minimal Indi server with a driver for things like opening and closing the roof, turning on and off lights, reading temperatures, reading level sensors on my mount etc. I could do this without Indi .. but I like the idea of wrapping all this in the Indo ecosystem so I can have a custom panel in Ekos for all these odds and ends. I'm comfortable with programming and understand the XML message passing "guts" .. but there are a few things I'm not clear about being a Kstars / Ekos newbie: (1) can Ekos connect to multiple Indi servers at once? (2) how do custom Indi control panels get made? Do they automatically "spring into being" based on the XML parameters advertised by the Indi device driver?
Thanks!
Read More...
Hello indi people,
I have an old webcam Philips SPC 900 NC I have modified for long exposure using the led control (so called lxled mod).
I was using it for quite some time with indi and was happy about it despite I had to happy a rather ugly patch to the indi-v4l2-ccd driver to make it work. The patch can be found in this thread: www.indilib.org/forum/development/8752-i...borting-capture.html
I recently upgraded indi to 1.9.8 re-applied my patch and installed but then the long exposure mode stopped working when trying to start exposing in php2 (loop mode) I get the message below (translated from french):
Unsupported type or read error when loading FITS fileAnd the loop stops here. No other error from the console where indiserver runs:
indiserver -v indi_v4l2_ccd indi_simulator_telescope ✘ INT 1m 55s
2024-05-16T22:02:21: startup: indiserver -v indi_v4l2_ccd indi_simulator_telescope
2024-05-16T22:02:21: Driver indi_v4l2_ccd: pid=507965 rfd=6 wfd=6 efd=7
2024-05-16T22:02:21: Driver indi_simulator_telescope: pid=507966 rfd=8 wfd=8 efd=9
2024-05-16T22:02:21: listening to port 7624 on fd 5
2024-05-16T22:02:21: Local server: listening on local domain at: @/tmp/indiserver
2024-05-16T22:02:21: Driver indi_simulator_telescope: HaAxis: TrackRate 1, trackingRateDegSec 15.041067 arcsec
2024-05-16T22:02:21: Driver indi_v4l2_ccd: Using default decoder 'Builtin decoder'
2024-05-16T22:02:21: Driver indi_v4l2_ccd: Supported V4L2 formats are:
2024-05-16T22:02:21: Driver indi_v4l2_ccd: Y16
2024-05-16T22:02:21: Driver indi_v4l2_ccd: NV21
2024-05-16T22:02:21: Driver indi_v4l2_ccd: BA81
2024-05-16T22:02:21: Driver indi_v4l2_ccd: YU12
2024-05-16T22:02:21: Driver indi_v4l2_ccd: NV12
2024-05-16T22:02:21: Driver indi_v4l2_ccd: YV12
2024-05-16T22:02:21: Driver indi_v4l2_ccd: BYR2
2024-05-16T22:02:21: Driver indi_v4l2_ccd: RGB3
2024-05-16T22:02:21: Driver indi_v4l2_ccd: RGGB
2024-05-16T22:02:21: Driver indi_v4l2_ccd: GRBG
2024-05-16T22:02:21: Driver indi_v4l2_ccd: JPEG
2024-05-16T22:02:21: Driver indi_v4l2_ccd: MJPG
2024-05-16T22:02:21: Driver indi_v4l2_ccd: RGBO
2024-05-16T22:02:21: Driver indi_v4l2_ccd: RGBP
2024-05-16T22:02:21: Driver indi_v4l2_ccd: YVYU
2024-05-16T22:02:21: Driver indi_v4l2_ccd: YUYV
2024-05-16T22:02:21: Driver indi_v4l2_ccd: GREY
2024-05-16T22:02:21: Driver indi_v4l2_ccd: VYUY
2024-05-16T22:02:21: Driver indi_v4l2_ccd: UYVY
2024-05-16T22:02:21: Driver indi_simulator_telescope: snooping on GPS Simulator.GEOGRAPHIC_COORD
2024-05-16T22:02:21: Driver indi_simulator_telescope: snooping on GPS Simulator.TIME_UTC
2024-05-16T22:02:21: Driver indi_simulator_telescope: snooping on Dome Simulator.DOME_PARK
2024-05-16T22:02:21: Driver indi_simulator_telescope: snooping on Dome Simulator.DOME_SHUTTER
2024-05-16T22:02:21: Driver indi_v4l2_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2024-05-16T22:02:21: Driver indi_v4l2_ccd: snooping on Telescope Simulator.EQUATORIAL_COORD
2024-05-16T22:02:21: Driver indi_v4l2_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2024-05-16T22:02:21: Driver indi_v4l2_ccd: snooping on Telescope Simulator.GEOGRAPHIC_COORD
2024-05-16T22:02:21: Driver indi_v4l2_ccd: snooping on Telescope Simulator.TELESCOPE_PIER_SIDE
2024-05-16T22:02:21: Driver indi_v4l2_ccd: snooping on SQM.SKY_QUALITY
// When I connect using phd2 client
2024-05-16T22:02:41: Client 11: new arrival from 127.0.0.1:36214 - welcome!
2024-05-16T22:02:41: Driver indi_v4l2_ccd: VIDIOC_CROPCAP: Inappropriate ioctl for device
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Decoder usesoftcrop true
2024-05-16T22:02:41: Driver indi_v4l2_ccd: VIDIOC_ENUM_FRAMEINTERVALS: Invalid argument
2024-05-16T22:02:41: Driver indi_v4l2_ccd: VIDIOC_ENUM_FRAMEINTERVALS: Invalid argument
2024-05-16T22:02:41: Driver indi_v4l2_ccd: VIDIOC_ENUM_FRAMEINTERVALS: Invalid argument
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Decoder set format: YU12 size 320x240 bpp 8
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Decoder: Colorspace is 8, using default ycbcr encoding and quantization
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Decoder allocBuffers cropping false
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Class User Controls
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Brightness
2024-05-16T22:02:41: Driver indi_v4l2_ccd: integer
// enable the LXLED mode
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Contrast
2024-05-16T22:02:41: Driver indi_v4l2_ccd: integer
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Saturation
2024-05-16T22:02:41: Driver indi_v4l2_ccd: integer
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control White Balance, Automatic
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Menu items:
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Indoor (Incandescant Lighting)
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Outdoor (Sunlight) Mode
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Indoor (Fluorescent Lighting) M
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Manual Mode
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Auto Mode
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Red Balance
2024-05-16T22:02:41: Driver indi_v4l2_ccd: integer
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Blue Balance
2024-05-16T22:02:41: Driver indi_v4l2_ccd: integer
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Gamma
2024-05-16T22:02:41: Driver indi_v4l2_ccd: integer
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Exposure
2024-05-16T22:02:41: Driver indi_v4l2_ccd: integer
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Gain, Automatic
2024-05-16T22:02:41: Driver indi_v4l2_ccd: boolean
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Gain
2024-05-16T22:02:41: Driver indi_v4l2_ccd: integer
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Backlight Compensation
2024-05-16T22:02:41: Driver indi_v4l2_ccd: boolean
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Color Effects
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Menu items:
2024-05-16T22:02:41: Driver indi_v4l2_ccd: None
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Black & White
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Band-Stop Filter
2024-05-16T22:02:41: Driver indi_v4l2_ccd: boolean
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Auto contour
2024-05-16T22:02:41: Driver indi_v4l2_ccd: boolean
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Contour
2024-05-16T22:02:41: Driver indi_v4l2_ccd: integer
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Dynamic Noise Reduction
2024-05-16T22:02:41: Driver indi_v4l2_ccd: integer
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Auto White Balance Speed
2024-05-16T22:02:41: Driver indi_v4l2_ccd: integer
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Auto White Balance Delay
2024-05-16T22:02:41: Driver indi_v4l2_ccd: integer
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Save User Settings
2024-05-16T22:02:41: Driver indi_v4l2_ccd: button
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Restore User Settings
2024-05-16T22:02:41: Driver indi_v4l2_ccd: button
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Restore Factory Settings
2024-05-16T22:02:41: Driver indi_v4l2_ccd: button
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Class Flash Controls
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Strobe
2024-05-16T22:02:41: Driver indi_v4l2_ccd: button
2024-05-16T22:02:41: Driver indi_v4l2_ccd: Control Stop Strobe
2024-05-16T22:02:41: Driver indi_v4l2_ccd: button
2024-05-16T22:02:42: Client 12: new arrival from 127.0.0.1:36222 - welcome!
// starting exposing in loop with a duration of 0.5s
2024-05-16T22:03:07: Driver indi_v4l2_ccd: Decoder reset crop
2024-05-16T22:03:07: Driver indi_v4l2_ccd: Decoder allocBuffers cropping false
2024-05-16T22:03:07: Driver indi_v4l2_ccd: setlexstate to 2
2024-05-16T22:03:07: Driver indi_v4l2_ccd: setlexstate to 0No error neither in the INDI console
Reverting to 1.9.7 makes the cam work again. After investigating a bit further I nailed down that particular commit: github.com/indilib/indi/commit/d3e668303...9e0e92f0680c4717e791
As it was introduced very late in this release I tried reverting it and the newly compiled package works nicely. However of course, further commits in 1.9.9 require that change and so I can't upgrade any further.
I took a look at the commit and on its own it just looks like fairly innocent change rename 2 functions and changing some of their arguments...
I have no idea why this messes up with the cam and I'm seeking for help fixing that. If possible I'd rather avoid another ugly patch so I'm more seeking for guidance/answers and better understand the problem, so I can hopefully try to fix it myself in the right way (despite my limited knowledge of C and hardware coding :-/ )
Let me know if specific information would be required
Read More...
Thank you again Aaron for the pointer to
that github page
.
My Player One Uranus-C is uncooled but it certainly looks like the same issue.
I will try to compare (a) compiling from source vs (b) using ubuntu ppa packages (and update the github page with relevant information, if any).
Read More...
Also, the Raspberry Pi download page needs to be removed or redirected to the source compile page:
www.indilib.org/get-indi/download-rpi.html
Read More...
How to Clean Your Cricut Mat: Learn the Top 3 Methods Here
A Cricut mat can become dirty after several uses. Sometimes, they may start losing their...
Show more
How to Clean Your Cricut Mat: Learn the Top 3 Methods Here – Cricut Explore
Found your cutting mat dirty? Learn how to clean your Cricut mat here. This post discusses the top 3 methods to clean the mat and…
Hi everyone,
I know this is supposed to work if you've filled in the "Observer" and optical train sections in Ekos, but I still have "Unknown" or wrong values to the FITS headers TELESCOP (shows the mount rather than the telescope), OBSERVER (shows "Unknown") and OBJECT (shows "Unknown" regardless of object name).
If I go to the INDI settings and change manually the Observer name from the CCD camera settings, then that works, but I have to redo it at the start of every session. That also won't solve the TELESCOP and OBJECT names.
I am using the latest Kstars/Ekos (Build: 2024-04-01T20:50:13Z) on the client computer (laptop running ArchLinux), and a relatively recent version of the INDI server (2024-05-16T09:45:03) running on a RPi 4 (not StellarMate, just a regular Raspbian Buster with the Astroberry repo added and indi-full installed).
Am I missing an obvious and simple tick box somewhere?
Read More...
Hi Hades,
Thank you for responding. Unfortunately, the "Celestron SCT" focuser driver does not have a 'Reverse Motion' option and the 'Direction' option does not serve this function -- it only sets the direction if you use the 'relative position' function beneath it ... it does not reverse the direction when using the Ekos autofocusing routine.
-Bret
Read More...
Thank you - I deleted the entire ~/.indi directory and that helped quite a bit. The errors are now gone.
But the Player One Uranus-CCD Indi Control Panel is still missing the temperature display that used to be there before my apt upgrade. I also have a ZWO ASI120MM Mini camera, and its Indi Control Panel shows the temperature.
Read More...
I am using AF3 focuser from DeepSkyDad and in the driver options there is one control which enables me to change the direction of motion. You can check, if such option is also in driver for your focuser.
Read More...
Hi John,
Thanks for the quick response ... much appreciated. Do you mean the "Direction" option under the Indi tab (see attached screenshot)? If so, this has no affect when using Ekos autofocus.-- it only effects the direction when I use/set the "relative position" field located right below it.
Are you referring to a different option under the Indi tab?
-Bret
Read More...
indi-allsky should be able to use the GPS device directly, but it will not be able to directly utilize the SQM device. It would be nice if there were a generic SQM type device and a simulator that could be used to test it, but I am unaware of that.
Read More...
Hello,
I still cannot make a relation between my INDI Touptek Driver 2.1 and your numbers. But I see at lunchpad that some drivers may be old. Because there was no feedback which leads to a solution, we decided to drive 2 hours to our remote site and get back the computer. I made a fresh install to linuxmint 21.3 (was 20.x), installed INDI new from ppa and now the camera works.
Thomas
Read More...